Best of www.BestZips.com (Collector's Edition)

home *** CD-ROM | disk | FTP | other *** search

/ Best of www.BestZips.com (Collector's Edition) / Best of WWW.BESTZIPS.COM Collector's Edition (JCSM Shareware) (JCS Marketing).ISO / db_appls / csw310.zip / CSLAVEW.1 / CSLAVEW.REV < prev next >

Wrap

Text File | 1997-01-04 | 127KB | 2,351 lines

CompuSlave For Windows Revision History 01-04-96 ■ Version 3.10 . Build 46 - Fixed a display problem where the text on the mini-browser and full browser status bars was being chopped off in 1024x768 resolution when using large fonts. . Build 45 - Added the users registration name to the about box for easier identification of whether the program has been registered or not. . Build 44 - Fixed a problem where the startup database would not be loaded at run time if it was compressed and the ".dat" name had been specified in the Startup Database field on the Preferences screen. . Build 43 - Released to beta testers. . Build 42 - Moved the new Options menu to the right of all of the database-specific menus when a database is open. Now, this menu should appear just prior to the Window menu. . Build 41 - Updated many of the Quick Tips, which were outdated after the implementation of the Preferences screen. . Build 40 - Added copyright information for 1997 to the status bar. . Build 39 - Increased the width on several of the speed buttons on the database editing screen for users who have 1024x768 resolution and are using large fonts. . Build 38 - Increased the width on the database speed buttons and the Preferences button on the main toolbar. This aids users who are using a screen resolution of 1024x768 with large fonts. . Build 37 - Fixed a problem where the Response button on the database editing screen was being corrupted if the Speed Button Display was set to "Text Only". . Build 36 - Fixed a problem where the routine that checked hard drive space available prior to decompressing a database was not being executed correctly, causing erroneous error messages to occur. (Error messages would state that "...0 bytes of hard drive space will be needed to decompress this file. Only 1.6 gigabytes are available..." etc.) The filename of the compressed file was not being assigned prior to checking the disk space requirements. . Build 35 - Fixed a problem where errors were not being trapped and reported when checking the hard drive space required to decompress a compressed database. . Build 34 - Fixed a problem where the Import Wizard dialog box was sizeable. Changed it to be a standard non-sizeable dialog box. . Build 33 - Fixed a problem where the Import Wizard was not remembering the last import filename when the OzWin, TapCis, or CompuServe Ascii Capture File options were selected. (This was broken in the Build 30 beta release.) . Build 32 - Fixed a couple of typos on the Import Wizard. . Build 31 - Added the options for Show Messages Added After Import and Show Tool Palette On Open Database into the Preferences screen. These options existed before, but had not been placed into the new Preferences screen. . Build 30 - Released to beta testers. . Build 29 - Removed the Modem button from the database screen. Replaced it with the Preferences and Current DB speed buttons. Removed the Settings tab from the database screen. . Build 28 - Finished adding descriptions for each of the options on the new Preferences screen. . Build 27 - Removed the tabset from the main CompuSlave window. All primary options are now within immediate view. . Build 26 - Removed the Modem and Help buttons from the main form of CompuSlave. Moved the Preferences button next to the Batch button, and adjusted the positioning of all buttons accordingly. . Build 25 - Removed the Status tab on CompuSlave's main form. . Build 24 - Changed the name of the "Communications" menu option on the File menu to "STSI Com". . Build 23 - Removed the Status menu. Moved the Database Status menu option to the Options menu. . Build 22 - Eliminated the Register menu. Moved the Registration Info menu item to the Help menu. Moved the Order CompuSlave option to the Help menu. . Build 21 - Moved the Current Database menu option from the Settings menu to the Options menu. Eliminated the Settings menu. . Build 20 - Removed the "OzCis, TapCIS, etc" Options menu item from the Settings menu. These options have been moved to the Preferences screen. . Build 19 - Removed the Compression Options menu item from the Settings menu. These options have been moved to the Preferences screen. . Build 18 - Removed the Defaults, CompuServe Info, Import Options, and Network Options from the Settings menu. All of the options from these dialog boxes can be found on the new Preferences dialog box. . Build 17 - Removed the Confirm Before Import INI setting. This value will no longer be used due to the implementation of the Import Wizard. The Import Wizard contains a final page that basically provides the same functionality as an import confirmation dialog box. . Build 16 - Removed the Use Activity Log INI setting. This value will no longer be used. The determination of whether to use an activity log will be based upon whether a valid activity log file exists in the Activity Log field on the preferences screen. . Build 15 - Removed the Auto Load Startup Database INI setting. This value will no longer be used. The determination of whether to use a startup database will be based upon whether a valid database file exists in the Startup Database field on the preferences screen. . Build 14 - Added support to the Import Wizard to scan the CompuServe v3 File Cabinet before attempting to import messages. The scan process detects which forums are included in the file cabinet and displays them in a "Forums Found" list box. The user can then move any or all of the forums to the "Forums To Import" list box. . Build 13 - Added support to make sure the new CompuServe v3 File Cabinet format could be saved as an import file format to the global INI and database INI files. . Build 12 - Consolidated all options from the Compression Options, Defaults, Import Options, Network Options, and Register dialog boxes onto one Preferences screen. . Build 11 - Added an Options menu to CompuSlave's main screen, and added a Preferences menu item. . Build 10 - Added a check when importing E-mail messages from a CompuServe v3 File Cabinet to make sure the From and To fields are assigned. If either field is blank, the user's CompuServe information (User Name and User ID) is inserted into the field. Also assigned a section name of "CompuServe Mail" to all E-Mail messages, since they have a section number of 0 (zero). . Build 9 - Added an option to the Settings menu where users can access/modify the CompuServe information (User Name and User ID). . Build 8 - Added new options to CompuServe for a CompuServe User Name and CompuServe User ID. If these values are blank, CompuSlave will prompt the user for these values on program startup. If the user decides to import CompuServe forum message from a CompuServe v3 File Cabinet, these values will be used when the "From" field is blank on private e-mail. . Build 7 - Added a check to exclude messages from being imported from a CompuServe v3 File Cabinet if the message body field is empty. . Build 6 - Added a check to make sure the CompuServe v3 File Cabinet importing routine is cancelled if the 500 message database limit is reached. . Build 5 - Added an option to the Import Wizard to allow users to import forum messages and/or e-mail messages from their CompuServe v3 File Cabinet. . Build 4 - Added initial support for an Import Wizard, to aid users when attempting to import messages into CompuSlave. . Build 3 - Excluded the CompuServe v3.x file cabinet from the loop that prompts the user to delete the file after a successful import. The CompuServe v3 file cabinet should never be deleted by CompuSlave. . Build 2 - Added a new progress indicator for the CompuServe v3.x file cabinet. Since it would be difficult to calculate the number of messages that will be imported, a new status screen will be used for this routine. . Build 1 - Added initial support for reading the new CompuServe v3.x file cabinet file (FCABINET.DAT). 11-19-96 ■ Version 3.01 . Build 5 - Addressed a problem where numerous messages in some CompuServe forums were failing to import into CompuSlave correctly when they were imported from a capture file. It appears that messages are being re-posted in some forums, without having a proper date/time format. ("2:7:36" vs. "02:07:36", and "2-Oct-96" vs. "02-Oct-96") These changes were causing errors in CompuSlave's conversion routine. The new conversion routine should recognize either format. . Build 4 - Removed the minimize and maximize icons from the title bars of many dialog boxes. . Build 3 - Improved the appearance of several dialog boxes by adding panels to section off the controls from the buttons. . Build 2 - Fixed a problem where the Copy, Paste, and Delete options on the Edit menu were not working properly if the selected field was the message body. (The Cut option was executed whenever one of these options was selected.) . Build 1 - Fixed a problem where CompuSlave did not stop importing WinCIM/CSNav messages if the user selected Cancel on the status screen. Instead, an error message would be generated for each of the remaining files, stating that there were errors reading each of the files. . Note: New message capacity calculations: Each message in a CompuSlave database consumes at least one SECTION in the database, with most messages consuming at least 3 or 4 sections. The maximum number of sections that can be stored in one database is 2,147,483,647. The largest STSI database contains 342,025 messages, which consume 1,922,707 sections, taking up 192,270,800 bytes of disk space. (That's approximately 5.6 sections per message.) This equates to an approximate database capacity of 382 million messages. However, due to the 2 gigabyte file size limitation of 16-bit applications, the practical limit is about 3.8 million messages. This limit may vary due to the length of each message in the database. 08-03-96 ■ Version 3.00 . Build 91 - Changed CompuSlave's behavior when attempting to rebuild or reorganize a database. If the process is not completed successfully, either because the user cancelled it, or an error occurred, the index file is automatically deleted. (In this instance, it is corrupt anyway, and should not be used. Leaving it behind could cause problems when accessing the database.) . Build 90 - Changed the database opening routine to check for valid index data in all eight index fields before allowing a database to be successfully opened. . Build 89 - Fixed a problem when attempting to open a database if the index file did not exist. If the user cancelled the rebuilding process before the index had been completely rebuilt, CompuSlave would attempt to close the database a second time, even though it was already closed. This caused an error message "Invalid Fileblock" to occur. . Build 88 - Fixed a background color problem on the pictures used on the Ok, Cancel, Help, and Close buttons when high-color mode was being used. . Build 87 - Updated documentation and help files with new help topics. Linked new topics into CompuSlave. . Build 86 - Changed the behavior of the Search One Field and Search Range dialog boxes for the section field. Users must now enter the section number for the search string(s), instead of the complete section strings. (This had to be changed as a result of the version 3.0 database reorganization.) . Build 85 - Changed the behavior of the GoTo dialog box for the section field. Users must now enter the section number to go to, instead of the complete section string. (This had to be changed as a result of the version 3.0 database reorganization.) . Build 84 - Removed the specific dialog boxes for TapCIS, OzCIS, WinCIM/CSNav, and CIS ASCII Capture Files, and created one dialog box to combine all of the options related to these specific file formats. . Build 83 - Made the WinCIM/CSNav file imports more tick-friendly to other Windows applications. . Build 82 - Fixed a tab order problem on the Current Database Options screen. . Build 81 - Added a Windows message processing loop to the file filtering process that occurs when importing a TapCIS, OzCIS, or CIS capture file. This allow other events (mouse clicks, etc) to be processed while the file filtering takes place. . Build 80 - Hid the Cancel button on the status screen that appears when the database INI files are being read for the Batch Import process, and also for the Database Status screen. . Build 79 - Fixed a problem where an error message "This program has caused an illegal operation..." could occur after terminating CompuSlave. (This behavior was noted on a Windows 95 system after executing any one of several WinSock applications.) This odd behavior was introduced after implementing a status screen in the file filtering process prior to importing a TapCIS, OzCIS, or CIS capture file. The behavior was only present when using the Batch Import feature. It appears that this behavior is related to a compiler problem when displaying a stay-on-top non-modal window on top of a modal dialog box. Worked-around this issue by disabling the stay-on-top modal window in batch mode. Instead, when file filtering is performed, the status bar on the bottom of the Batch Import screen is updated with the status text. . Build 78 - Added a "Save All" button to the Convert Message screen that appears during the reorganization process when a user selects the Examine All or Examine Range options. This will allow the user to save all records, thus cancelling the examination process without cancelling the reorganization. . Build 77 - Added an "Abort" button to the Convert Message screen that appears during the reorganization process when a user selects the Examine All or Examine Range options. This will allow the user to cancel the reorganization process more easily. . Build 76 - Fixed a problem where the reorganization process was not being terminated immediately if the decompression of a compressed database failed. . Build 75 - Added a fail-safe check to make sure that the Full Browser cannot be wider or taller than the coordinates of the screen. If CompuSlave detects this condition when displaying the Full Browser, the coordinates are reset to the default. . Build 74 - Changed the default size of the Full Browser. The initial size will be determined based on the screen resolution of the monitor. Each of the outer limits will be offset 50 pixels from the edge of the screen. . Build 73 - Added the ability for CompuSlave to remember the Full Browser's size and position on the screen. This is a global setting. . Build 72 - Added the ability for CompuSlave to remember the Full Browser window state (normal, minimized, or maximized). This is a global setting. . Build 71 - Added a command to erase the backup copy of the database INI file that is created during a reorganization process. . Build 70 - Merged the reorganization and version 2.x database upgrading options to allow users to reorganize a version 2.x database. This automatically converts the structure to the version 3.x format. (In earlier builds, the database could only be converted to the new format when it was opened using the File Open command.) . Build 69 - Added support for CompuSlave to remember the last view state (normal, mini-browser, or message-only) for the current database. This value is saved to the Database INI file and restored the next time the database is opened. . Build 68 - Added a check to make sure a database file (or zip file) exists before putting it on the initial history list when CompuSlave is executed. . Build 67 - Added support to automatically update the title on the currently open database after the user selects Ok from the Current Database dialog box. (This needs to be updated in case the user changed the Database Description while editing the Current Database options.) . Build 66 - Fixed a potential problem where the database INI file was being re-read when the "Current Database" option was selected from the Settings menu. Because of this, any unsaved database INI settings would have been lost. Now, the database INI file is not re-read upon selecting this option. It is, however, still written when Ok is selected from this dialog box. . Build 65 - Added a Database Description field to the New Database dialog box to allow users to specify the database description when the database is initially created. . Build 64 - Added a Database Description field for each individual database to allow users to describe the name/contents of the current database. This setting can be changed on the Settings, Current Database screen. . Build 63 - Added "*.plx" to the WinCIM/CSNav import file filter. Since this is an INI file setting, existing users will want to change this manually on the Import Options screen. . Build 62 - Made the default message number for WinCim/CSNav's *.plx messages to be message number 1. Modified the database record adding routine to not issue duplicate message number warnings for these types of messages. . Build 61 - Added a message tagging limit check on the Tag Range dialog box to make sure a user cannot tag more than 16,368 messages. If this limit is reached, the tagging is automatically stopped. . Build 60 - Changed the text on some of the tips on the CompuSlave Tips dialog box. . Build 59 - Fixed a problem where CompuSlave could not tag more than 16,368 messages. Previously, message boxes indicated that the limit was 16,384, but this value was incorrect. Changed the Tag All routine to check this limit and stop tagging before attempting to tag more than 16,368 messages. (Previously, a "List Index Out Of Bounds" error message would be issued.) . Build 58 - Added a new option to the Defaults dialog box on the Data Validation page. The new option allows users to specify whether or not a message number 0 causes a data validation error. . Build 57 - Modified the RegCheck.Exe program for new version / registration control. . Build 56 - Changed the registration code processing routine in CompuSlave to require new version 3 registration codes. (Version 2.x users will need to upgrade to version 3 for a registration fee of $30.00.) . Build 55 - Fixed a problem on the data validation screen to put the text "NONE" into the "Response" field. (A -1 is used to denote no response within the database. After the version 3.0 conversion, this field was containing a -1, instead of "NONE".) . Build 54 - Added a TapCIS Format option to the import file dialog box. . Build 53 - Fixed the printing format routines to include the section name in addition to the section number on the printouts. (This was not working as a result of the version 3.0 database reorganization.) . Build 52 - Limited the Subject, From, and To starting and ending range fields to 30 characters on the Tag Range dialog box. . Build 51 - Added a "Fuzzy Match" check box to the Subject, From, and To tagging categories on the Tag Range screen. This allows CompuSlave to find all messages with extra characters on the "Ending Range" value. (The ending range value is thus padded with character #255.) . Build 50 - Fixed a problem where the 500-message limit nag screen would be displayed multiple times when importing messages from WinCIM/CSNav *.msg, *.thd, and *.plx message files. This routine now checks to see if the message limit has been exceeded, and if so, immediately exits out. . Build 49 - Added a status screen to the import file filtering process to indicate the completion percentage of the filtering. . Build 48 - Made sure that when a database is created using the Extract Tagged Messages process, the status screen displays the correct database name (using a ".dat" extension). . Build 47 - Changed the Tag Range routine for the subject, from and to fields. Previously, the ending range field was padded with character 255, to ensure that all names within the range were included. After further consideration, this behavior may not be desirable. Users must specify the complete ending string that should be included in the tag range. . Build 46 - Fixed a problem where CompuSlave was not saving new section names to a new or existing database during an extract tagged operation. (This was necessary after the version 3.0 database reorganization code was added.) . Build 45 - Increased the number of times that CompuSlave gives up ticks during the import routines for OzCis/OzWin, TapCIS, and Ascii Capture Files. . Build 44 - Added a quick tip to CompuSlave's Quick Tips screen about the ability of STSI to accept CompuSlave registrations using SWREG on CompuServe. (Use program ID #12174) . Build 43 - Updated the registration codes for version 3.0. This will require that users of CompuSlave version 2.x upgrade to the new version. (Upgrade fee is $30.00 for a single-user license.) . Build 42 - Added an "Ignore Message Number 0 (zero)" option to the TapCIS Options dialog box. Added the ability to ignore these messages during the import process when this option is turned on. . Build 41 - Modified the Tag Range process to automatically stop looking for messages to untag if the total tagged message count equals zero. . Build 40 - Added an option to cancel the tagging / untagging process when the Tag Range option is being used. . Build 39 - Added a "TapCIS Options" option to the Settings menu. Created a dialog for special options applying to TapCIS imports. . Build 38 - Fixed alignment issues on the Tag Range dialog box. Removed the Tag All option from this dialog box since it is already present from the Editing screen. Added a status label to indicate the total number of sections in the current database. Changed the status bar on this dialog box to read "Total Messages Tagged". . Build 37 - Added an option to the Tag Range dialog box to untag all messages contained in the specified search criteria. . Build 36 - Implemented the new Tag Range features to allow users to tag messages within a range of dates, message numbers, or from and to names. Automatically update the status bar on the Tag Range dialog box as message numbers are being tagged. . Build 35 - Added options to the Import Options dialog box to turn import file filtering on or off and to optionally preserve the original import file. If the original file is not preserved, the new filtered file overwrites the original. The filtered import file is created either in the user's temporary directory (if it exists on the path), or in the CompuSlave directory if the user's temporary directory does not exist on the hard drive. . Build 34 - Added a filtering option for import files. At STSI, we ran into several captures files that contained a #0 (null character) in between a carriage return and line feed combination, as detected using a hex editor. This caused errors when CompuSlave attempted to read the import file, resulting in subsequent data validation errors. To fix this problem, CompuSlave can optionally perform a filter of the file prior to an import, removing all #0's from the file. (This character should not be in a normal import file anyway.) . Build 33 - Added options to the Tag Range dialog box for users to tag all messages within date or message number ranges. Also added an option for users to tag all messages within a specific section. . Build 32 - Added a "Tag Range" option to the Tagged menu and a button to the Tagged tool bar for users to access options for tagging records within user-specified ranges. . Build 31 - Fixed a problem where the background editing screen was not synchronizing the display to the same record that was displayed in the full browser. (This was broken as a result of the database reorganization, and was NOT a released bug.) . Build 30 - Added section length checking to determine what version of CompuSlave the database was created with. This value is used to determine the version of the database (version 2.x vs. version 3.x). If an invalid section length is detected, the value is not valid, and CompuSlave will not allow the database to be opened. . Build 29 - Verified that CompuSlave could successfully decompress database files prior to performing a version 3.0 reorganization, and compress them following the successive database closing procedure. . Build 28 - Added support for reading WinCIM's *.PLX message format. . Build 27 - Fixed the new Date and Time field controls to be read- only when they are not being edited, and to be the same color (silver) as the rest of the editing fields. . Build 26 - Fixed a problem where CompuSlave would try to continue to open the database after a version 3.0 reorganization failed. . Build 25 - Made sure that the reorganize routines properly detected an INI version of 2.x (Windows version) or 1.x (CompuSlave For DOS) in order to upgrade the database to version 3.0. . Build 24 - Added specialized Date and Time formatted edit controls for displaying the Message Date and Message Time fields. . Build 23 - Changed the behavior of the status screens. Previously, the user could accidentally close the screens by pressing Alt-F4, which is standard Windows behavior. Since the Cancel button wasn't pressed, the user wasn't prompted whether or not he wanted to end the current process. The status screen was closed, but the operation would be continued until it was completed. Now, the Alt-F4 combination (or a mouse click on the close box) automatically invokes the Cancel button's click method. . Build 22 - Changed key identifiers within the code to prevent eventual confusion with similar names belonging to other objects. . Build 21 - Fixed a problem where Saving an edited message was not working after converting to the new database structure. . Build 20 - Addressed a problem where CompuSlave was attempting to compress a database after successfully converting it from a version 2.x to a version 3.x database. The attempt to compress the database occurred after the conversion, but before the file was actually opened. (This occurred if the Database Compression setting was set to Prompt Before Compress or Compress Always for the individual database.) Disabled the compression that would normally occur right after the conversion process. . Build 19 - Fixed a problem where extra messages would be found when a search entire message search was performed. This was due to the fact that the message record buffer was not being cleared in memory before getting each record. (This was introduced as a result of the new version 3.0 database structure, and was not a problem in previous versions of CompuSlave.) . Note: The new database structure used by CompuSlave v3.00 can significantly reduce the size of the database and index files when compared to version 2.xx. Our tests indicate that the .DAT file is about 30% smaller (range 26% - 34%) and the .IX file is about 5% smaller. . Build 18 - Changed the title on the reorganization status screen to "Converting Database" when a database is being converted from version 2 to version 3. Also added the name of the database being converted to the title. . Build 17 - Added a "Do you wish to convert this database to version 3?" prompt before converting a database when it is opened. . Build 16 - Changed the mini-browser and full-browser section column to display section names the same way that version 2.xx did. . Build 15 - Fixed a hotkey conflict on the Compression Confirmation dialog box. . Build 14 - Recoded portions of the Search Entire Message routines to decode messages before searching them for user-specified strings, and encode messages before adding them to the new search results database. . Build 13 - Added an error check and message to detect when a user attempts to reorganize a version 2.x database. The reorganization process cannot be selected until the user has rebuilt the database in the new version 3.0 format by simply opening it with CompuSlave. . Build 12 - Added a conversion routine to automatically detect CompuSlave version 2.x databases and convert them to the new version 3.0 format when they are opened. . Build 11 - Made sure that the I/O layer used to encode/decode the storage buffer completely clears the storage buffer before performing an add record or get record operation. Added the same support to the reorganization routines. . Build 10 - Added an additional error message to detect/report a problem if a user attempts to overwrite an existing database when the database is being accessed by his own or another computer system. . Build 9 - Fixed a problem where the database INI file was not being cleared properly when a new database was being created, if it was overwriting an old database by the same name. (The values from the old file were being read, the file was erased, and the new one was created using the old values. Changed the order of operations to erase the INI file first, and then create the new INI file.) . Build 8 - Added a date/time key to allow messages to be sorted by the date and time that they were created. . Build 7 - Added support to decode the storage buffer each time a row needs to be rebuilt for one of the browsers. . Build 6 - Added a length byte to offset 4 of the storage buffer to inform CompuSlave's database routines what the exact length of each message record is. . Build 5 - Modified the database structure to eliminate fixed-length string fields. Each string field is started with a length byte, and successive string fields follow immediately afterward, with no white space in between. Implemented a storage buffer variable, and routines to encode or decode the storage buffer before reading or writing a new message to the database. . Build 4 - Reduced the data stored in the section field to just storing the section number (and sub-section code) in the database and index files, and creating a cross-reference with the database INI file. . Build 3 - Removed support for CompuSlave For DOS by eliminating conditional defines. (CompuSlave For DOS will no longer be supported by STSI, since the Windows version is far more advanced, making the DOS version not as practical.) . Build 2 - Started initial planning for database reorganization to make databases and index files much smaller and more compact. Converted the Date and Time fields (formerly stored as strings) to a numeric representation for database storage. 07-03-96 ■ Version 2.23 . Build 4 - Fixed a problem where the parsing routines were not working on the Date and Time fields for TapCIS message file imports. (This was broken in version 2.22, in an attempt to fixing the parsing routines for OzCIS/OzWin users. Both message formats should now import messages without data validation errors.) . Build 3 - Fixed a problem where CompuSlave could appear to hang when importing messages from an OzCIS/OzWin file. When attempting to parse a paragraph of text, it was possible that the word wrapping routine would get caught in a recursive loop. This happened if a single character on the beginning of a line was followed by more than 79 characters of "white space" (spaces, carriage returns, line feeds, etc.). . Build 2 - Fixed a problem where the hotkeys could not be used on the import dialog box. (Focus fields had not been set up.) . Build 1 - Fixed a tab order problem on the import dialog box. 06-14-96 ■ Version 2.22 . Build 7 - Added a limit of 5 total databases in the UNREGISTERED version of CompuSlave. . Build 6 - Fixed a problem where a CompuSlave import could appear to hang when attempting to import OzCis/OzWin messages if a line in the message body contained a pound sign (#) as the first character. . Build 5 - Fixed a problem where all message body text imported from CIS formatted files was being stripped of leading spaces. This appears to have been broken in versions 2.13, 2.20, and 2.21. . Build 4 - Fixed a problem where OzWin/II message files could receive data validation errors on the date and time fields during an import operation. This occurred if the line that contains the date and time in the OzWin file contained a pound sign on the line prior to the date. . Build 3 - Fixed a problem where the global default Import File Format option (on the Import Options screen) was not being saved to disk properly. . Build 2 - Fixed a problem where a GPF would occur if the user attempted to Cancel an import of an OzCIS/OzWin file. . Build 1 - Fixed a tab order problem on the import dialog box. 05-30-96 ■ Version 2.21 . Build 102 - Fixed a problem on the Extract Tagged dialog box when users attempted to extract tagged messages to a new database. If the user did not specify the CompuSlave directory on the front of the database name field, CompuSlave would use the current directory. While this was likely to be the CompuSlave directory anyway, it was possible that this could have been the import directory instead, if the user had just finished an import operation. . Build 101 - Removed the "Register" button from the Settings tab on the database editing screen. . Build 100 - Fixed a problem where (unrelated) errors messages would occur if a user attempted to open a database twice when the network type was set to None. Now, CompuSlave checks to see if the database is already open before attempting to open it, and issues an error message if the database is already open. This only takes place when the network type is None, so network users can still open multiple copies of a database without this limitations. . Build 99 - Hid the Register and Status menus when a database is opened to allow enough room for all of the menu options. (This is needed because the menu was too wide for 640x480 resolution under Windows 3.1.) . Build 98 - Added a short delay prior to closing the Compression Status screens to make it evident that the gauges have reach 100%. . Build 97 - Fixed problems where Help was not linked in to various dialog boxes throughout CompuSlave. . Build 96 - Changed the behavior of CompuSlave's database browsers to ALWAYS be synchronized, no matter what operation is being performed. When a record position is changed from within the Full Browser, the record position within the Mini-Browser is automatically updated, and the record displayed in the normal view also reflects the new position. . Build 95 - Fixed a problem where files on the File menu's history list were not always being removed from the list while the database was open. . Build 94 - Updated a vendor's library (used for some memo windows and status bars) to the latest version. . Build 93 - Made a source code change in a vendor's library on their request. This changed fixed a potential GPF when cutting all text from a special memo editing field. (Due to CompuSlave's behavior, our users should not have seen this problem.) . Build 92 - Changed the default set of Import File Filters to include a "WinCIM/CSNav (*.msg;*.thd)" filter. (This will only appear on new installations of CompuSlave. Existing users may want to manually add this file filter to the file filter list, if they wish to import these types of files.) . Build 91 - Assigned hot keys to each of the new options on the Import Options dialog box. . Build 90 - Addressed several issues with the new Import File dialog box. Assigned hot keys for the three available file filters. Assigned the proper tab order. Added proper handling for directory and file mask changes, and proper processing of a double-click on the file list box. . Build 89 - Investigated the possibility of reading and importing WinCIM *.PLX message files (e-mail messages), but since these messages are not part of a forum, they do not have a section number, a section name, or a response to field, and thus are not readily compatible. Determined that these message types should not be imported into a CompuSlave database. . Build 88 - Changed the appearance of the dialog box that prompts the user whether or not to compress a database when it is closed. Added an option to allow the user to change the permanent setting of the database compression value, without having to re-open the database to make the desired change. . Build 87 - Fixed a problem where the memo window was not read-only. (This was broken in version 2.20.) . Build 86 - Added support to import message threads (*.THD files) directly from the WinCIM or CSNav file cabinets. . Build 85 - Added I/O checking to the WinCIM file read routines to make sure that the entire message contents can be read accurately. . Build 84 - Added a default Import File Format to the Import Options screen. Available options are CIS, OZCis/OzWin, and WinCIM/CsNav. This setting is used as a global default value, and can be overridden for each existing database. . Build 83 - Fixed a problem where an error message would be displayed that the Import Path entered on the CompuSlave Defaults screen did not exist. This error message now states that the Import Path is on the Import Options screen. Also fixed a problem where the Import Path field could contain a ".." in the path if the Browse button had been used to search for a path. This could cause the error message to be displayed. . Build 82 - Change the import file dialog box to allow the user to specify which type of import file format to use when reading the import files. Available types are CIS format (generated by using a capture file from a terminal program), OzCis format, and WinCIM format. (Other formats may be added in the future, if necessary.) . Build 81 - Added support to import messages (*.MSG files) directly from the WinCIM or CSNav file cabinets. . Build 80 - Added support to import messages from a file generated by OzCis/OzWin (*.MSG Format). . Build 79 - Fixed a problem where the Mini-Browser was not maintaining the same record position after the current sort order was changed from inside the Full Browser. . Build 78 - Fixed a problem where the Mini-Browser was not maintaining the same record position after changing the current sort order. . Build 77 - Changed to a different method of locking the search results database memo window to prevent flickering. This method is superior to the old one, making the flickering unnoticeable. . Information - Each message in a CompuSlave database consumes at least one SECTION in the database. The maximum number of sections that can be stored in one database is 2,147,483,647. The largest STSI database contains 303,253 messages, which consume 860,048 sections. This equates to an approximate database capacity of 757 million messages. However, due to the 2 gigabyte file size limitation of 16-bit applications, the practical limit is about 2.7 milliion messages. This limit may vary due to the length of each message in the database. . Build 76 - Modified several of the status gauges to use the newer style contol. . Build 75 - Added a status message box to inform the user if no files are found to delete on the "Cleanup" option. . Build 74 - Added a check to determine whether other users are actually using the database before attempting to reorganize it on the current workstation. (This check only occurs when Novell or MSNet is used for the network type.) If other users are accessing the database, the reorganization process is aborted. . Build 73 - Added the ability for CompuSlave to erase all *.CSF, *.DSF, and *.RSF signal files in the cleanup process. . Build 72 - Created a reorganization lock file that is used to warn other network users that a reorganization process is taking place. This file is created before the reorganization starts, and erased after the reorganization finishes. . Build 71 - Added a check to ensure that the database is not being reorganized by another user before attempting to decompress or compress it. . Build 70 - Added compression and decompression conflict checking before attempting to reorganize a database. This process assures that no other users are compressing or decompressing the database. . Build 69 - Locked the new text editor window during updates to minimize flickering. (Search results database only.) . Build 68 - Enhanced the appearance of the status bars on the compression status screens. . Build 67 - Fixed a GPF problem that would occur after the "Page Fault" error was fixed in Build 66. This GPF was caused when CompuSlave attempted to determine the number of network users in a database prior to an attempt to compress it. This problem only occurred if the user cancelled a reorganization process, and answered Yes to compress the database. (This problem was also introduced in version 2.20.) . Build 66 - Fixed a problem where a "Page Fault" error would occur when reorganizing a database after the user cancelled the reorganization process. (This problem was introduced in version 2.20.) . Build 65 - Added an option to enable/disable the message box that displays the number of messages added to a database following an import operation. (This setting can be modified from the Import Options dialog box.) . Build 64 - Added an option to enable/display the confirmation dialog box that appears prior to importing a file into the database. (This setting can be modified from the Import Options dialog box.) . Build 63 - Added support for selecting multiple import files from the import file dialog box. (Use a CTRL-Click to highlight multiple files within the dialog box.) . Build 62 - Changed the right-click popup menu in a search results database to only contain a "Copy" option. The Cut, Paste, and Delete options do not apply since messages in a search results database cannot be edited. . Build 61 - Changed the search text highlighting color back from white on maroon to the default highlight color (usually white on navy). . Build 60 - Fixed a problem where extra text would intermittently appear to be highlighted in a search results database. Fixed this problem by forcing a repaint of the memo window after displaying a new message. . Build 59 - Added support to use mouse highlighting in the alternate text editing control used for a search results database. . Build 58 - Modified the Memo display window to use a standard Windows memo for a normal database, and an alternate text editing control for a search results database. . Build 57 - Linked in the updated compression libraries. . Build 56 - Changed the default Printing font to Courier New, Pitch=10. (The previous setting was Courier New, Pitch=20.) Since this setting is remembered between CompuSlave sessions, users upgrading from a previous version will need to make this change manually by accessing the Font option from the Print dialog box. . Build 55 - Fixed a problem where printing a message on a printer would produce very small print. (This was due to a bug in the programming language.) . Build 54 - Added an option to the Import Options screen to allow the user to control whether Duplicate Message Numbers are always added to the database, never added to the database, or whether a dialog box pops up to prompt them for each message. . Build 53 - Removed the "Sort by..." sub-menu from the popup menus on the Full Browser and Mini-Browser screens. This sub-menu has been replaced with a "Sort" menu option that links to the Sort Database dialog box. . Build 52 - Created a common routine for retrieving the names of database files from the CompuSlave directory. This routine is used by the Batch Import and Database Status processes. . Build 51 - Added a status indicator when reading the database .INI files when Databases is selected from the Status menu. . Build 50 - Added a status indicator when reading the database .INI files during a batch import. . Build 49 - Modified the mini-browsers column widths to be automatically updated to match those of the Full Browser when the columns are resized. . Build 48 - Added context-sensitive help to the New Database screen. (This was previously omitted.) . Build 47 - Added a speed button to the Register tab on the main toolbar for the Order CompuSlave option. . Build 46 - Fixed a problem where the Cut/Copy/Paste commands were not working in edit mode. Also fixed a problem where the Delete key mapping was not working in the new text editor. . Build 45 - Corrected a problem where the Last Import Time was not being displayed properly on the Batch Import and Database Status forms. . Build 44 - Added support for CompuSlave to remember the width of the columns in the Full Browser and Mini Browser for each database. . Build 43 - Added a filtering status display to the full browser to show the status of the filtering process. This process can take a considerable amount of time on large databases. . Build 42 - Disabled the automatic update timer for the full browser if not in network mode. . Build 41 - Added speed-buttons to the bottom of the Full Browser for the Sort, Tag, and Column Order options. . Build 40 - Added a speed-button panel to the bottom of the Full Browser. Added a speed-button to turn message filtering on or off. This allows users to view only the tagged messages in the browser. Also added an option to the popup menu to turn filtering on/off. . Build 39 - Changed the way the Last Import Date and Time is displayed on the Batch Import and Database Status forms to show "None" if no imports have been done. (Or none have been logged to the .INI file.) . Build 38 - Added a section to the Batch Import screen to indicate whether the import file exists on disk. . Build 37 - Added network file locking for writing to the activity log file. . Build 36 - Added a speed button to the Status tab on the main toolbar for the Databases option. . Build 35 - Moved the code from the BatchImportClick event procedure into the BatchStatusForm.FormCreate procedure. . Build 34 - Added a Status, Databases option to display statistics about the databases in the CompuSlave directory. . Build 33 - Enhanced the response buttons on the toolbar and tool pallette by providing additional visual indications of the number of responses to a given message. If there are no responses, the button icon will appear disabled. If there is one response, the button icon will be red. If there is more than one response, the button icon will be green. . Build 32 - Fixed a problem where the SlaveFindRecordMultiple function was very slow at searching through the index for message responses. . Build 31 - Added a "Replies" indicator on the database screen to indicate the number of responses to a given message. . Build 30 - Modified the SlaveFindRecordMultiple function to return the number of responses to a given message. . Build 29 - Changed the color of the search text highlighting from white on blue to white on maroon. . Build 28 - Fixed a horizontal scroll problem on the new text editor. . Build 27 - Improved the appearance of the standard status screen. . Build 26 - Removed the list box control that was used to display the message body field on a search results database. Previously, this was the only control that would support highlighting of multiple strings in the message body text. We have replaced this control with a new text editing control that supports the highlighting of multiple strings. . Build 25 - Added additional quick tips. Deleted a duplicate tip. . Build 24 - Added a "Delete activity log" button to the defaults screen. . Build 23 - Changed the type of viewer used to display the log file text from the defaults screen. The previous viewer was limited to a maximum file size of 32K, and an "unable to insert a line" error message would be issued if the size of the log file was greater than 32K. The new viewer can handle files up to 2 Gigabytes in size. . Build 22 - Added an option to the Register menu to print an order form for CompuSlave. This form, once completed, may be FAXed, sent, or uploaded to STSI. . Build 21 - Fixed an obscure problem where a "List Index Out of Bounds" error would occur when opening a database if the database INI file could not be read due to a lock error. Also fixed a problem where the default column order for the database browsers was not being set if the database INI file could not be read after a lock error. . Build 20 - Added a status screen to show lock file progress. . Build 19 - Added network file locking for reading INI files when the user selects the "Batch Import" option. . Build 18 - Updated the caption on the Delete dialog box to say "Delete Database". . Build 17 - Added an option to the Utilities sub-menu to clear the history list. Added separator bars to the Utilities sub-menu. . Build 16 - Added a Registration Information button to the Register tab on the main window's toolbar. Added safety code to make sure the main window's toolbar displays the first page, and that the tab names match the page names of the toolbar. . Build 15 - Changed the main screen graphic. . Build 14 - Added a compression/decompression progress indicator that displays in bytes. (This offers an additional indication of progress, especially on large files where the percentage bar may not reach 1% for a time.) . Build 13 - Added speed buttons to the first page of the toolbar to give users quick access to the last five open databases. . Build 12 - Reset the DatabaseVersion value inside the Database INI file to the current program version when a database reorganization is completed successfully. . Build 11 - Added an "Order CompuSlave" option to the Register menu. . Build 10 - Changed the toolbar on the main window to have multiple pages accessible by clicking on a tabset. Added a separate Register menu, and moved the Register and Registration Information options to this menu. Added tabs to the multi-page toolbar for each of the menus. . Build 9 - Fixed a problem that occurred when multiple users attempted to access the same database using the Novell or MS-Net network settings. A dialog box was previously displayed prompting the 2nd user whether he wanted to use the compressed or decompressed version of the database. We now check to see if other users are accessing the database before displaying this prompt. If other users are in the database, no decompression is performed and the database is opened normally. . Build 8 - Changed the print tagged feature to print messages in true message number order. . Build 7 - Fixed a problem where the Print Tagged Messages feature was printing messages in reverse order (newest to oldest). Messages are now printed in chronological order (oldest to newest). (This method actually prints the messages in "record number order", which may not be identical to the message number order.) . Build 6 - Fixed a problem where if the user answered "No" to the reorganize confirmation prompt, both the .DAT and .ZIP files would remain on a compressed database. Fixed a problem where resources were not being released if the user answered "No" to the same prompt. . Build 5 - Added the ability to change the "Compress Message Data" setting from the reorganize database form. . Build 4 - Expanded the text of an error message that is displayed if the number of files in a ZIP file is found to be zero. The error message now explains that this can be due to the non- existence of XCDZIP.DLL or XCDUNZIP.DLL in the user's Windows System directory. . Build 3 - Added a Settings and a Window page to the toolbar on the database editing screen. Added all options from the Settings menu to the Settings page, and added all options from the Window menu to the Window page. . Build 2 - Changed the Search Status Form to fsStayOnTop. This prevents the search status form from getting "lost" until the search is complete. . Build 1 - Changed the border style on the compression status and search status screens so it is not sizeable. Changed the gauge color on the search status screen from yellow to blue. 04-25-96 ■ Version 2.20 . Build 70 - Fixed a problem where a GPF (0002:7347) would occur if the Emergency Exit option was selected from the Help menu when one or more databases were open. (Internal fix only... This problem did not appear in the released version.) . Build 69 - Fixed a problem where the "Messages have been tagged..." warning dialog appeared twice when clicking on CompuSlave's main window system menu (the close box). Moved database closing checks out of the OnCloseQuery event to the OnClose event. (Internal fix only... This problem did not appear in the released version.) . Build 68 - Added a "Confirm Before Exiting CompuSlave" option to the Interface tab on the Defaults dialog box. This will cause CompuSlave to prompt users for confirmation before they exit the application. Fixed a couple of hot key conflicts on the Interface tab on the Defaults screen. . Build 67 - Modified the Extract Tagged Messages option to allow the extraction of messages to a compressed database. The Browse dialog box now allows ZIP files to be selected. . Build 66 - Updated the documentation, help file, and help file links with the latest changes. . Build 65 - Made sure hot-keys were assigned to controls on all dialog boxes, and that there were no hot-key conflicts. . Build 64 - Fixed tab order problems on the data validation dialog box. Fixed a problem where there wasn't a hotkey assigned for the Search Entire Message option on the Search Type dialog box. . Build 63 - Implemented a new XCDUNZIP.DLL file, to fix a problem in a vendor's library. Previously, if the user cancelled a decompression process, the file being extracted was not closed, and therefore could not be deleted in a cleanup process. The open file could also cause problems if the user immediately tried to decompress the database again. Internal testing shows that this (non-released) bug has been fixed. . Build 62 - Built in support for 4 separate "Match Case" check boxes on the Search Entire Message screen. This allows one of the separate settings for each of the four group boxes on this screen. . Build 61 - Modified the behavior of the Test Archive Integrity option. If the user cancels the testing process, he will be prompted whether to erase the non-compressed database, erase the compressed database, and take no action. . Build 60 - Changed the behavior of the editing fields on the Options tab of the Defaults screen. When the Use Activity Log check box is not checked, the Log File Name field will be disabled. Likewise, when the Auto-Load Database On Startup check box is not checked, the Startup Database Name field will be disabled. . Build 59 - Combined the compression, decompression, and test ZIP integrity status screens into one screen that can be modified depending on the current operation. . Build 58 - Implemented a new status screen for the Search Entire Message process. The new screen is much more visually appealing, and contains room to display the entire search criteria used in the search process. Removed most of the description fields from the Defaults, Compression Options, and Current Database screens. The extensive number of options being added requires that these description fields be removed to make room for the bare necessities. . Build 57 - Added code to manually show the progress bar at 100% before closing the rebuild/reorganize status window. . Build 56 - Added a safety check to make sure the user is warned before creating a new database if an existing database already exists in compressed form. The user is warned that the compressed database will be overwritten if he chooses to continue. . Build 55 - Added a status screen to the Test Zip Archive option to show the user the file being processed and the percentage completed. . Build 54 - Added a Test Zip Archive option to allow users to test the integrity of a compressed database before CompuSlave deletes the original database. Added a check box to the Compression Options screen to enable or disable this option. Turned off the Move Files option for the ZIP compression, since the database files will be manually deleted once the integrity test is successful. . Build 53 - Reworked the order and placement of code that performs the database compression and query to save a search results database. The prompt to compress a database now occurs after the editing form for the database has been hidden from view. . Build 52 - Added checking to make sure than CompuSlave can read the CompuSlave INI file during the initial execution. If this file cannot be read (usually due to a locking error), the application will issue an error message and terminate. . Build 51 - Added support for compressed .ZIP databases to the Reorganize Database option. Users can now browse for a compressed database and CompuSlave will decompress the database prior to reorganizing it. CompuSlave also re-compresses the database based on the setting of the Database Compression option in the individual database INI file. . Build 50 - Modified the batch import routine to make sure that a compressed database name is not added to the list of databases in the table if a non-compressed database with the same name already exists in the table. . Build 49 - Deleted the backup database if the user selected not to continue once he was informed of the Compress Data setting. Erased the INI file when the user selected Delete Database from the Utilities menu. . Build 48 - Narrowed up the Tag column on the database browser. Disabled the Reorganize Database option when 1 or more databases are open. Fixed a character case problem on the reorganization backup database status screen. . Build 47 - Verified that the proper compression and decompression operations take place when batch imports are in process. Made necessary adjustments and corrections. . Build 46 - Rewrote the routine that performs text highlighting in a search results database to handle up to 9 search strings. . Build 45 - Removed the compression information from the Reorganize Database dialog box. Since this information is now contained inside each individual database's INI file, CompuSlave cannot display the compression state before the database is selected. . Build 44 - Changed the caption on the Database Options screen to display the name of the database being modified. Also changed the wording on the built-in help screens on the Compression Options dialog box. . Build 43 - Updated the vendor's library for the database engine and database browsers. This update includes some minor changes for Windows 95 support and browser fixes. . Build 42 - Added the capability for each database to have separate settings for the "Compress Data" and "Database Compression" settings. Added a new option to the Settings menu called "Current Database" that allows the user to change these settings in the currently open database. The default value will be set to the global setting assigned by the user on the Compression Options screen. . Build 41 - Added an Import Options menu option to the Settings menu and created an Import Options dialog box to manage all import-related settings. Moved the import-related options from the Defaults dialog box to the Import Options dialog box. Added an Imports speed button on the main form's toolbar for quicker access to the Import Options dialog box. . Build 40 - Combined the Compress Entire Database and Prompt Before Compression options into one value called Database Compression. The user can select to Never Compress Databases, Prompt Before Compressing Databases, or Always Compress Databases. . Build 39 - Added a Compression button on the main form's toolbar for quicker access to the Compression Options dialog box. . Build 38 - Added a Compression menu option to the Settings menu and created a Compression Options dialog box to manage all compression-related settings. Moved the Batch and Compression pages from the Defaults dialog box to the Compression Options dialog box. . Build 37 - Added the ability to cancel the rebuild index process that occurs when a database is opened with a missing or corrupt index file. A new status screen shows the percentage completed and gives the user a Cancel button to terminate the process. . Build 36 - Corrected a problem where the .LCK file was not getting erased when a search database was created. This would generate a "Lock error on the file ... .INI". . Build 35 - Added a new page called "Batch" to the Defaults dialog box for the batch import process. Added a setting to control the compression of databases during the batch import process. This setting allows users to either compress all databases after an import is complete, compress none of the databases after the import is complete, or only compress a database that was in compressed form before the import process was started. . Build 34 - Added a setting to allow the user to specify whether CompuSlave prompts him prior to compressing a database. The default is TRUE. If this option is turned off, the database is automatically compressed when it is closed. . Build 33 - Added an option to do nothing (No Action) if the user cancels the compression process. . Build 32 - Added safety checking to make sure that if the user cancels the compression process, he will be prompted whether to delete the old compressed database, or the newer non-compressed database. (This situation will only exist if the database had been previously compressed, and the ZIP file still exists in the CompuSlave directory.) . Build 31 - Modified the file filters on the Batch Import, Add, Browse For Database dialog box to include options for ZIP files. . Build 30 - Added a safety check to make sure that a ZIP file has a corresponding INI file before adding it to the table displayed on the batch import screen. (Since database INI files were introduced in version 2.10 of CompuSlave, users upgrading from a version prior to 2.10 will simply have to open and close a database for the database INI file to be created. This will allow a compressed database to be automatically added to the batch import screen for possible selection.) . Build 29 - Added the ability for the batch import process to search for compressed ZIP files to include in the batch import process. ZIP files that are found are added to the table for possible selection by the user. . Build 28 - Implemented file locking for the database INI files to ensure that 2 users on a network or multitasking system cannot attempt to read or write to these files at the same time. (This process uses atomic lock files.) . Build 27 - Implemented a file locking system for the file CSLAVEW.INI to ensure that 2 users on a network or multitasking system cannot attempt to read or write to this file at the same time. (This process uses atomic lock files.) . Build 27 - Changed the compression routines to store the database INI file outside of the ZIP file. (This allows the batch import routines to work properly, and provides flexibility for future enhancements.) . Build 26 - Added a setting to the Interface page of the Defaults dialog box to allow the user to specify whether a search results database is opened in a cascaded, tiled, or maximized window. . Build 25 - Added safety code to clean up (erase) extracted files if the user cancels the decompression process. This will leave only the compressed .ZIP file in the directory. . Build 22 - Turned off the option on the Open File dialog that forced the filename to exist before CompuSlave would open it. This will allow users to enter a filename with a DAT extension, even though the actual filename may have a ZIP extension. . Build 21 - Modified the open database routines to automatically look for and open a compressed database if the uncompressed database file does not exist. . Build 20 - Added a check to make sure that other network (or multitasking) users are not accessing a decompressed database if an attempt is made to decompress a compressed database that has the same name. If another user is accessing the database, the current user is not allowed to decompress over the top of it. . Build 18 - Added a check to make sure that other network (or multitasking) users are not accessing the database prior to attempting to compress it. . Build 15 - Added a check to make sure there is enough free space on the target drive before attempting to decompress a compressed (.ZIP) database. This check takes into account the cluster size on the target drive. . Build 14 - Added support for highlighting up to 9 different search strings in a search results database. This was necessary after enhancing the search capability to include more options (See Build 12). . Build 13 - Fixed a problem where the Find operation could cause a general protection fault when the user searched for text containing more than one word. Recursion caused the GPF, so the routine has been rewritten to eliminate the possibility of recursion. Also fixed a problem where the Cancel button on the Find dialog box was not receiving a mouse click, making it difficult to cancel a Find procedure. This was due to the fact that the background (Main) window was receiving the focus after a new message was displayed. Disabled the code that switches the focus to the main form if the Find dialog box is displayed. Added a confirmation dialog to the Cancel option on the Find dialog box. This will confirm that the user wants to cancel the Find before the process is actually terminated. . Build 12 - Expanded the search capability on the "Search Entire Message" screen. User can now enter text in up to 12 fields, using a combination of AND/OR/NOT statements. . Build 11 - Changed the order that files are added to the compressed file list. Now we add the smallest files first. This makes the status screens work better. Added checks to ensure that no compression or decompression is in progress before deleting the compressed file. . Build 10 - Added signal file support to manage simultaneous compression of databases. Corrected some minor centering and sizing problems on the Compression and Decompression status forms. . Build 9 - Changed the behavior of the decompression routine to overwrite existing files. . Build 8 - Added signal file support to manage simultaneous decompression of compressed databases. . Build 7 - Added a decompression status screen to display the progress of the decompression process. . Build 6 - Changed the name of the "Messages" tab to "Validation" on the Defaults notebook. Added a "Compression" tab, and moved the Compress Message Data check box to this tab. Added option to enable/disable compressing the entire database using ZIP compatible compression. . Build 5 - Ensured that the database files were "added" to the compressed file if the compressed file did not exist, and were "updated" in the compressed file if the compressed file already existed. (The update option is extremely fast, since only changed files are updated.) . Build 4 - Added support for *.ZIP file filters on the "Open" and "Delete" file dialogs. . Build 3 - Added status routine for the database compression process. . Build 2 - Added support for storing the .DAT, .IX, .DIA, and .INI files in compressed form. (PKZIP compatible .ZIP file.) 02-28-96 ■ Version 2.13 . Build 214 - Enhanced the appearance of the "About" dialog box. . Build 213 - Fixed a problem where the current message was not begin reset after an "Extract Tagged" operation was completed. . Build 193 - Added Message Data compression status indicators on the Reorganize Database screen. . Changed the wording on the Tagged tab buttons to be more concise. (Example: "Print" changed to "Print Tagged") . Moved the "Compress Message Data" control from the Paths tab on the Defaults screen to the Messages tab. . Fixed a minor problem where the response number field was not being set to "NONE" if the sequence of characters at the beginning of the subject field was "#-". This would cause a data validation error to occur. . Enhanced the Reorganize Database option (on the Utilities menu) to allow users to examine records during the reorganization process to decide whether or not they should be included in the database when it is reorganized. Users can examine all records, or only records within a range of values (1 to 10, etc.). When a message is examined, the user is given the option of whether to save the message or discard it completely. Users can also view the message body text during the examination process. . Removed the minimize icon from the group of border icons on the Database Browser title bar and the View File dialog box title bar. (User should not be able to minimize a modal dialog box.) Added the ability for users to resize the View File dialog box. (This dialog box is used for viewing the activity log and for viewing message body text when a message fails the data validation check.) . Added a new tab on the Defaults screen for "Messages". This page contains a setting for Data Validation when saving messages to the database. Users can set data validation to "Prompt Before Adding Message" which instructs CompuSlave to prompt them if a message does not meet the import criteria specified by CompuSlave. The user will be shown a dialog box containing the message fields, and will be given the opportunity to add the message anyway, or discard it completely. Other options for Data Validation include "Never Add Message", which automatically rejects any messages that fail to meet the import criteria, and "Always Add Message", which causes CompuSlave to completely ignore the data validation check. Reasons that a message could fail a data validation check include: improper date format, improper time format, message number field does not contain a number, message number field contains a zero (0), response number field does not contain either "NONE" or a number, or the calculated size of the message body text exceeds 24K. Other validation checks may be added in the future, if necessary. . Modified the importing routine to make sure that data assigned to a field cannot be longer than the allowed field length. This should not happen anyway, since the field lengths are long enough to accomodate the associated field text. However, if a user attempts to import a capture file that is not formatted correctly, the data assigned could become too long, causing fields to be corrupt. Note to users: If you are using a terminal program such as QmodemPro, Procomm Plus, STSI Com, etc., and are capturing the text files as suggested in the documentation, you should not have to worry about problems like this. . Implemented newest version (.52) of database browser. . Fixed a problem where the INI file was not being renamed and/or moved if the user chose to save a search results database under a new name and/or in a new location. If the user was moving the database files to a new location, this would cause the INI file to remain in the temporary directory, so the temporary directory would not be deleted. (No errors were reported to the user, but the remaining directory could be noticed underneath the CompuSlave directory.) If the user simply renamed the database, the INI file would be left in the directory under the old name, and a new INI file would be created the next time the saved database was opened by CompuSlave. . Fixed a problem where the error message "One or more of the files could not be renamed. The temporary database has not been deleted." would occur when attempting to save a search results database if the user attempted to rename and/or relocate the database files. CompuSlave was attempting to rename/move the .DIA (dialog) file that is created in network environments. This problem only occurred if the network type was set to "None", and was not a problem for Novell and MS-Net network types, since the dialog file exists in those situations. . Added support for the plus key (+) to move the database to the next message and the minus key (-) to move the database to the previous message. Also added support for using the ENTER key to move the database to the next message. These key mappings are not valid when a record is being added or modified. . Added enhancements to CompuSlave's printing support. Added the ability to print a range of messages, allowing the user to specify the starting and ending message number. Also added an option to print the messages using CompuSlave's import file format. This format should match the exact format used by CompuServe when messages are captured using an ASCII terminal program. . Added support for CompuSlave to remember the current sorting order of a database between sessions. . Added support to automatically change the sort field on the mini- browser view when the sort field is changed from within the Full Browser. Also added support to automatically update the column order in the mini-browser when the order in the Full Browser is changed. Made sure that the highlight bar position is maintained no matter which of the previous actions are performed. . Added support for users to change the column display order within the Full Browser. (Also added this ability to the mini-browser view.) This setting can be different for each database. (Display order is written to the database's INI file.) . Added hot-keys to the tabs on the Defaults screen. . Fixed a minor display problem where the 2nd and 3rd lines of the "Please Wait" dialog were not being cleared when the Batch Import option was selected. This could cause left-over text from a previous operation to be displayed on these lines. . Changed the behavior of CompuSlave's sort feature. Previously, CompuSlave would reset the database to the first record after the user changed the sort field. Now, CompuSlave will stay on the current record, no matter what the sort field was changed from or to. (The order of display will simply be changed.) . Changed the tagged indicator on the batch status form to make a tagged line more obvious. (A triangle is drawn to the left of the selected database.) . Enhanced the mini-browser to have column dividers, a proportionally-spaced font, sizeable headings, and incremental search capability. . Changed the Tag/Untag key in the database browser from a space to the F10 key. The space key is now used in the new incremental search feature. . Added a Tag/Untag option to the pop-up menu. . Created a pop-up menu within the database browser to give users the ability to change the field used for sorting. Built in support so that the browser automatically maintains its position on the current record when the sort field is changed. . Enhanced the database browser to have column dividers, a proportionally-spaced font, sizeable headings, and incremental search capability. . Added user customization of the import file filters. A new tab was added on the Defaults screen to allow users to enter up to 5 import filters. (The first import filter listed will be the default.) These import filters will be used on the Import File dialog boxes, allowing users to change which types of files are displayed in the file list. . Added a file history list to the File menu. CompuSlave will display the last database files that were opened (up to five total). Users can now select the database name directly from the File menu to open it. 01-11-96 ■ Version 2.12 . Fixed a potential problem where corruption could be displayed in the message fields if the user deleted the last message in the database. . Added a warning message to the tag all process to alert users that they cannot tag more than 16,384 messages at one time. . Updated copyright notices for 1996. . Changed the size and position of the floating Tool Palette to allow room for 2 additional speed buttons. Added the Open Database and Close Database buttons to the Tool Palette. Moved the Time and Keyword fields directly below the Date field to make room for the larger Tool Palette. . Swapped the First through Last buttons on the "Messages" tab of the toolbar with the Browse through Sort buttons. . Added Tag All and Untag All buttons to the "Tagged" tab on the toolbar to allow users to tag and untag all messages in the database with one command. The Tag All command is limited to tagging 16,384 messages. . Added a warning to alert users if they try to close the database when messages are tagged. The warning message gives users the opportunity to cancel the close process, in order to perform an action with the tagged messages. . Enhanced CompuSlave's printing support. Added the ability to print the current message, tagged messages, or all messages in the database. Added a Font button to the Print Dialog to allow users to change the default font, size, color, etc. that is used when messages are printed to the printer. Added other options to break between pages, untag messages after printing, and prompt to continue if an error should occur. Added status screens to the print tagged and print all options to allow users to cancel the printing process. . Added an "Extract" button to the "Tagged" tab on the toolbar. Added support to allow users to extract all tagged messages and place them in another new or existing database. (After this process, the messages will remain in the existing database, but can be removed easily by selecting the "Delete" button and deleting all tagged messages.) . Added a "Print" button to the "Tagged" tab on the toolbar. This will allow users to print either the current message or all of the tagged messages. . Added a "Delete" button to the "Tagged" tab on the toolbar. This will give users the option of deleting all tagged records. . Added a "Tagged" tab to the toolbar at the top of the editing screen to manage operations related to tagged messages. . Added a "Tag Message" check box to the Normal view, and an option to tag a record from the browser or mini-browserr screens by pressing the space bar. . Fixed a minor problem where the focus would automatically shift to the message body field when using the "Mini-Browser view". This would be inconvenient for the user, since pressing the down arrow in the Mini-Browser would automatically transfer the focus to the bottom portion of the screen, forcing the user re-select the Mini-Browser before being able to press the down arrow key again. . Improved the appearance of the status screens. . Added a "Please Wait" dialog box that will be displayed before the Batch Import screen is displayed. This is necessary because CompuSlave has to search for a list of database names, and their accompanying import files. This process can require a little time, especially if the user has a large quantity of database files in the CompuSlave directory. . Added a minimize button to the Batch Import screen to allow users to minimize the entire CompuSlave For Windows application until the batch import process is finished. (This was especially necessary for Windows 95 users, since Windows 95 does not provide an easy way to return to the desktop or click on desktop icons if a large modal dialog box is in the way.) . Fixed a typographical error on the Network Options screen and on one of the Quick Tips. . Fixed a problem where vertical scroll bars were not appearing on the message body's memo window when the Mini-Browser or Full- Screen message views were used. 12-14-95 ■ Version 2.11 . Version 1.01 of STSI Com is included in the new CompuSlave package. Added many enhancements / improvements to STSI Com, including: -> CompuServe Settings screen for Name, User ID, Password, and Host Name. -> New Phonebook Layout. This will require users to set up any phonebook entries from scratch. Previously, users could not specify a different Com Port, Baud Rate, Parity, etc., for each phonebook entry. The new layout allows these settings, as well as a user-defined login script. STSI Com can optionally create a default CompuServe login script using the information entered on the CompuServe Settings screen. -> Phonebook Defaults screen to allow users to enter the default Com Port, Baud Rate, Parity, Data Bits, Stop Bits, etc., for each new entry in the phonebook. . Added a proper title to the title bar on the "Batch Add" dialog box used for adding a database to the Batch Import process or editing an existing database. (Previously, the title had been left as "Dialog".) . Spruced up the Register, Network Options, and Registration Information screens. . Performed minor cosmetic changes to the Defaults screen and the About screen. . Changed the help context on the View Activity Log screen so the "Defaults screen" help appears when Help is selected, instead of the Table of Contents. . Added the "Tip #" to the title bar of the CompuSlave Tip screen, so users can tell what Tip they are viewing, and when they have reached the end of the Tips. . Fixed a minor problem where the same CompuSlave Tip would appear each time CompuSlave was executed. Now, a tip is chosen at random. . Modified the questionaire in the REGISTER.DOC file. . Changed the caption on the Batch Import screen to "Batch Import" instead of "Batch Import Status". Removed the bold attribute from the font on the bottom half of the buttons on this screen. 12-03-95 ■ Version 2.10 . Fixed a problem where CompuSlave was not highlighting text when using the Find option if the text to be found contained more than 1 word and the words were separated in the message body by a line break. . Fixed a problem where CompuSlave was not highlighting search phrases in a temporary search results database if the search phrase contained more than 1 word and the words were separated in the message body by a line break. . Added "Last Import Date" and "Last Import Time" fields to the Database INI files to keep track of the last date and time that an import was performed on each database. Added columns for these values to the Batch Import screen, so users can quickly view this information. . Expanded the documentation and help files to include information about new options. Sectioned up the help file into smaller chunks, and greatly improved CompuSlave's context-sensitive help system. . Changed the behavior of CompuSlave to automatically return the focus to the message body field after a user selects Next, Previous, First, Last, and most of the other buttons. This allows users to immediately press the PgUp and PgDn keys to view the text of the message, without having to click the mouse in the message area first. . Added an option to the Defaults screen to allow users to specify whether or not a confirmation dialog box is displayed before a message can be deleted. This option is ON by default, which means that users will be prompted to confirm a message deletion. . Added support for CompuSlave to beep when a duplicate message is found and the user is prompted with a warning/confirmation dialog box. This will aid users who leave their computer somewhat unattended during the import process. . Noted a problem that occurred when using a Novell NetWare 4.1 network in combination with Windows 95. Attempting to open a database with the "Novell" network type specified would result in a "Fileblock cannot be opened in net mode" error message. During the process of tracking down this problem the file/product "Microsoft Service For NetWare Directory Services" dated October 1995 was installed. After this installation the error message reported above could not be reproduced. . Changed the wording of an error message that can occur if an attempt is made to open a database with a corrupt or missing index file. Previously, the error message stated that the database was missing. The new error message indicates that the file is either missing or corrupt. . Added initial support for batch imports. Added an option to the Utilities menu called "Batch Import". Added a Batch Import dialog box that display a list of available databases in the CompuSlave directory, along with the default import filename for each database. Multiple databases can be selected from the list to be included in the import process. When the Start button is selected, CompuSlave begins to open each database, import the selected text file, close the database, and continue with the next selected database. As much as possible, message boxes will be disabled during this process, to attempt to prevent unnecessary user intervention. (See new section in documentation and help file.) . Modified the default behavior of the CompuSlave Tips screen to display the tip after CompuSlave's main window has been displayed. . Added an option to the Help menu to allow users to access CompuSlave's Tips screen at any time during normal program operation. . Added a "CompuSlave Tip" screen that will be displayed on startup to give the user quick tips about special features and settings in CompuSlave For Windows. This screen can be disabled by de-selecting the "Show Tips On Startup" check box. New tips will be added on a regular basis. . Added a sample database to the distribution package called SAMPLE.DAT. (An index file, SAMPLE.IX, is also included.) This will allow first-time users to see how CompuSlave works, without having to create a CompuServe capture file immediately. (Also, the file IMPORT.TXT has been renamed to SAMPLE.TXT.) . Added STSI's CIS address (76300,3066) to the About box information. (When contacting STSI via CIS, users should address correspondence to Craig Stevenson.) . Added an option to the Defaults screen to instruct CompuSlave to beep when the import process is complete. The default is ON. . Removed the version stamp from the title bar of CompuSlave's main window. Instead, the version can be viewed from the About box available from the Help menu. . Re-adjusted the default pop-up position of the Tool Palette to be placed directly above the memo field, but underneath the Keyword field. . Decreased the height of the Tool Palette title bar to consume less space. (This required the removal of the close box on the upper left corner.) Also changed the layout of the Tool Palette to have only 2 rows, but 11 columns of speed buttons. Changed the position of the Date, Time, and Keyword fields to accomodate the new size of the Tool Palette. Added the New Message, Edit Message, Delete Message, Save Message, Cancel Edit, and Hide Tool Palette buttons to the Tool Palette, based on user request. . Changed the title on the Tools pop-up window to "Tool Palette". 11-12-95 ■ Version 2.00 . Updated the Setup program to exclude the installation of the Borland Database Engine, since this is no longer needed for the new database structure. Also added an enhancement to warn users before a file will be overwritten in their \WINDOWS or \WINDOWS\SYSTEM sub-directories. This will give the user more control over what files are installed, especially if duplicates exist. Also added support for the Setup program to create a SETUP.LOG file in the destination directory. This file will contain a list of all files that were successfully placed on the hard drive during the installation process. . Added support for users to double-click on the close box of a maximized MDI child window to trigger a close event. (This overrides default Windows behavior that does NOT automatically close an MDI window when a double-click occurs on the close box of that window. Internal Reference #444973) . Added code to create, read, and write an INI file for each individual database. (If the database is named TEMP.DAT, the INI file will be named TEMP.INI.) Initially, this INI file will maintain the version of the database, and the name of the last capture file that was imported into the database. This will allow CompuSlave to "remember" capture file names between sessions. . Fixed a bug in previous versions of CompuSlave where multiple GPF's could occur after changing the font attributes of the memo field using the font dialog box. If the database was then closed, and any database was opened again in the same session, CompuSlave would issue multiple GPF's. The memory location for the font in the font dialog box was pointing to the global font setting for memo windows, due to a direct memory assignment. If the database window was closed, this memory was freed, resulting in the global font being unavailable for additional databases. . Added path checking to make sure that a new database is created in the default CompuSlave directory, if no drive and/or path is specified in the Filename field of the New Database dialog box. . Added an option to the Defaults screen to delete the capture (import) file after the messages have been imported into the database. The default for this option is OFF. . Added command line support to override the startup database file on the Defaults screen. Also added support for stacking the names of multiple databases on the command line, to instruct CompuSlave to open more than 1 database when it is executed. . Added a floating Tool Palette to display the most used speed buttons (copied from the main tool bar). Added an option to the Defaults screen for users to specify whether or not the Tool Palette should be displayed automatically when a database is opened. Added options to the Views tab and Views menu to Show or Hide the Tool Palette. . Changed the font on all of the dialog boxes from Arial to MS Sans Serif, which is easier to read. . Added an option to the Defaults screen to automatically load the Startup Database File when CompuSlave is executed. This box can be de-selected (unchecked) to disable the automatic startup file loading. . Added quick-key combinations for several often-used options, such as Ctrl+I for Import, Ctrl+F for Find, Ctrl+S for Search, etc. Added the display of these quick keys to the corresponding menu options. . Added a Reorganize Database option to the Utilities menu to allow users to rebuild a CompuSlave database. This is useful if the "Compress Message Data" option has been turned off, and you decide to enable compression. Rebuilding the database will compress all messages, saving considerable hard drive space. This feature is also necessary if one or more messages should somehow become corrupt. If corruption is found in the database, CompuSlave can ignore the corrupt messages during the reorganization process, thus deleting them from the resulting (newly rebuilt) database. . Added a Utilities sub-menu to the File menu and moved the Delete Database option onto this menu. . Added keyed field search options. New options include searching for a text string or a range of text (starting and ending strings) at the beginning of any one of the seven keyed fields. . Added a status window for the rebuilding process, in case the database index file (.IX) should become corrupt or is missing. . Arranged the menu options and titles to emulate the tab names on the speed button toolbar. . Added commands to disable the editing buttons (New, Edit, Delete, Save, and Cancel Editing) in a temporary search results database. Also disabled the Views options, since the search- word highlighting is only available in the Normal view. . Added commands to enable/disable selected buttons and menu options when the user selects the New or Edit Message options. (The user will not be able to browse, search, sort, etc., when they are editing a message. All options that are disabled during the editing process are re-enabled when Save or Cancel Editing is selected.) . Added search text highlighting in searched databases. If the Search String 1 or Search String 2 values appear in the edit fields or the message body, the text is highlighted. . Added Locate and Views menus to the main menu when editing a database. Reorganized menu options according to category. Made sure that all speed button options were also available on the menu system. . Added an option to the Default screen to allow users to turn off the "Current Message" update counter on the Search Status screen. When this option is turned off, the search can be completed 15% - 20% faster than if this value must be updated after every message. The default is on. Power users who need the speed will want to disable this option. . Implemented a new status screen, designed to display as much status information as possible, without slowing down the search process. . Added an option to the Defaults screen to view the log file, if one has been created. . Optimized the "Scanning Messages" dialog box that is displayed at the beginning of the import routine. This dialog box displays the number of messages that are found in the import file, incrementing the number display for each message. . Removed code (in the uses clauses) that required the distribu- tion of the file BIVBX11.DLL. Also removed all code that required use of the Borland Database Engine. . Verified that the display order in the Browse dialog box was changed accurately, depending on the current sorted field in the database. . Turned off sharing violation errors to allow CompuSlave users to open the same database on more than one workstation at a time. (This requires that either the Novell or MS-Net network options be turned ON from the Network Options screen.) . Removed the filtering options, since this functionality is not easily added to the new database structure. (This feature may be added back in at a later date, depending on user feedback.) . Disabled repetitive calls to the registration checking routine. Instead, set up a global variable that can be checked at a much more rapid rate, increasing speed for operations such as importing. . Added a check to detect if the import path is not valid when the import option is selected. A message box instructs the user where to change the default import path. If the import path does not exist, CompuSlave uses the current directory. . Added a status bar to the bottom of each database editing window. The status bar display the name and path of the open database, the number of total records, and the search criteria (if the database is a search results database). This infor- mation is updated each time a new record appears on the screen. . Added hot-keys to all Ok/Cancel button and linked field labels to editing controls on all dialog boxes. Verified that the tab order was accurate on all dialog boxes. . Fixed a problem when attempting to close the application. If a Find operation was being performed on a database, a message was displayed indicating that the user must cancel the find procedure before exiting. However, CompuSlave continued the exiting procedure anyway. CompuSlave now ceases the exit procedure if one of the database windows cannot be closed. . Removed the ability to size the Status dialog box that is used for searches and imports. Removed the maximize/minimize buttons from this dialog box. . Added an import dialog box that warns users when a duplicate message number exists in the database. The import dialog box allows users to add the new message anyway, skip the new message, add all duplicate messages, or skip all duplicate messages. . Added support to handle multiple responses to a message using the new database code. . Created tabs on the speed button display to allow users to access speed buttons according to their category. There are so many options available within CompuSlave, that tabs are necessary to manage the display of these speed buttons. Added an Edit tab for the New, Edit, and Delete buttons, and added a Print tab for the Print and Print Setup buttons. . Loaded all speed button icons into a resource file that is linked into the EXE file. These icons are loaded directly from the resource file when the speed button display is loaded or updated. . Added an option for users to display the speed buttons using Text and Picture together (default), Picture Only, Text Only, or no speed buttons. If users are in need of more screen space for viewing messages, they can have the option of making the buttons smaller, or not using them at all. In addition, beginners will appreciate the text and pictures which appear on each of the speed buttons, making CompuSlave easier to understand. This option may be modified from the Defaults dialog box. . Added support for CompuSlave to execute an external communications program (supplied by STSI). This will allow users to easily capture messages from CompuServe, without having to purchase a separate communications package. . Changed the CompuSlave database code to allocate a new message record buffer for each open database. (Since the database code was previously used in the DOS version, which has a non-MDI interface, a separate buffer for each database was not necessary prior to use in the Windows version.) . Added information to the GoTo dialog box to inform users that GoTo text must match, exactly, the contents of the field they are searching. . Added a "Temporary Database" designation to the title bar of a searched database. This informs users that they are viewing the results of a search they performed on a separate database. . Added an option to save a temporary search results database. When a full-text search is performed, CompuSlave creates a temporary database containing the search results. Before closing this search results database, CompuSlave prompts the user whether or not to save the database for future reference. The database can be saved in the same, or a different, directory, and it can be optionally renamed. . Changed the Print option to reflect format of the new database. . Added a "Find Previous" option to the Find dialog box. This allows users to go to the previous occurrence of the specified text, as well as the next occurrence (which is the default). . Set up the Window Menu to display a list of the currently open databases. . Changed the Network Users control on the Register dialog to a numeric/spin control. . Added help buttons to most of the dialog boxes within CompuSlave. . Implemented the startup file option, so CompuSlave will auto- matically load the startup file specified on the Defaults screen when it is executed. . Changed the options on the Defaults dialog box. Added options for an import path, startup file, and activity logging. Added Browse buttons to allow users to search for a particular import path and startup file. Made sure that users could select an open database as the startup file without receiving a sharing violation error. . Moved the speed-button panel INSIDE each of the MDI child windows in CompuSlave. This will allow easier processing of the events specific to each individual database. . Changed new databases to use ".dat" extensions, instead of the old ".db" extensions. Updated various file dialog boxes to support this change. . After much deliberation, STSI decided to change the format of the CompuSlave For Windows databases to be compatible with the CompuSlave For DOS databases. This is a MAJOR structural change, which required a complete rewrite of the database support within the program. . Increased the speed of importing capture files and CompuSlave For DOS database files. There is approximately a 350% speed increase when importing, over previous versions of CompuSlave For Windows. (The fields are no longer updated while the import is taking place, so users will not see changes taking place in the background while the import status screen is displayed.) 06-20-95 ■ Version 1.02 . Fixed a potential problem where a GPF could occur if a user attempted to close a database while 1) it was being searched for the purpose of creating a new temporary search database, 2) it was being created as a temporary search database, or 3) it was importing messages from a capture file or a CompuSlave For DOS database. Added a check to make sure that the database cannot be closed during the import process or the search process, until the import or search has been completed or cancelled by the user. . Fixed a problem where a GPF would occur when exiting CompuSlave if one or more editing windows were still open when the exit command was issued. This occurred because Windows needed to "Process Messages" immediately after each child window was closed. . Fixed a problem where CompuSlave was not remembering the background color on the memo field(s) after exiting and re-executing CompuSlave. . Removed several of the dialog boxes from the auto-create list, such as the About box dialog, the New File dialog, the Defaults dialog, and the Register CompuSlave dialog. This will reduce memory consumption and program overhead during CompuSlave's startup process. . Added a confirmation message to inform users that a database has been successfully deleted, or that one or more files could not be deleted after an attempt was made to delete a database from the File menu. . Modified the toolbar on the Browser to mimick the buttons displayed on the main (parent) window. Removed the Import button from the Browser window, and added a Find button instead. . Added an option to pack an existing database, reducing its overall size. Added a status window to let the user know that the database is being packed. . Fixed a problem where the Delete Database option on the File menu was not working properly. The database was not being deleted. . Added an option to "Match Case" in the Find dialog box. . Added a "Find Text" speed button to allow users to find text in the message body. This operation will find all occurrences of the user-specified text in the current message body, and then advance to the next record after all occurrences have been highlighted in the current message. A message box is displayed when the end of the database is reached. . Fixed a problem where CompuSlave was not erasing a temporary (search) database if the user exited the program without double-clicking on the system menu of the window belonging to the searched database. . Changed the Responses form to look at the secondary DataSource and Table when finding multiple responses to the current message. . Created a second DataSource and Table for searching operations to prevent changing the current position in the main table. . Added commands to disable the original and response buttons if an original message or response message does not exist. . Added 3 notebook pages to manage the new views added to the editing window. . Added buttons to the toolbar for a "Message Only View" and "Normal View" setting (in addition to the Mini-Browser button previously displayed. The Normal view provides the standard view, displaying all of the available message fields. The Mini-Browser view displays a grid on the top half of the form, showing several records in a table format. The Message Only view shows the entire message filling the window area. . Added support for the Setup program to add a Help File icon, and "Read Register.Doc" icon to CompuSlave's program group during the setup process. . Added the Cut, Copy, Paste, and Delete commands to the memo window's right-click popup menu. . Added an Edit menu with Cut, Copy, Paste, and Delete commands that will take effect for the editing and memo fields. 06-11-95 ■ Version 1.01 . Fixed a compatibility problem with the Setup program running under Windows 95 (Final Beta), where the Setup program had determined that the Borland Database Engine Installation had been completed, even though it was still running. . Changed the border style of the status form from Dialog to Normal. This will allow users to resize the status form and minimize it (or maximize it) within the program. This should make it much easier for users to import or search a database and perform other non-related operations at the same time. . Fixed a problem where importing 500 messages would trip an error message that more than 500 messages could not be added to a database in the unregistered version of CompuSlave. Since the import status screen is set to "Stay On Top" of all other forms in the program, the status screen would hide the error message, making it appear that the application was stopped or hung. (Pressing Alt-F4 would close the modal dialog, and return control to the program.) Changed behavior to automatically hide the status windows before display this (and other) modal message boxes. . Changed the size of the database message field that is stored in the database table. Previous value of 240 is now reduced to 1. Since most messages are longer than 240 characters, storing up to 240 characters in the database, (as well as the memo field) was redundant and space-consuming. This can end up saving users megabytes of storage space, depending on the size of the database. (A conversion utility from version 1.00 will be available in a future version.) 06-10-95 ■ Version 1.00 . Initial release of CompuSlave For Windows. (Released with the Borland Database Engine v2.50)